chore(deps): bump actions/setup-node from 4 to 6#1098
Merged
RemiliaForever (RemiliaForever) merged 1 commit intoJun 26, 2026
Merged
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
requested review from
David Qian (Davidqian123) and
Paul Zhu (vinovo)
as code owners
dependabot
Bot
added
the
github_actions
dependabot
Bot
requested review from
RemiliaForever (RemiliaForever),
AlexCHEN (alexchen4ai),
Mengsheng Wu (mengshengwu),
Zack Li (zhiyuan8) and
Perry Cheng (zhycheng614)
as code owners
Contributor
|
Dependabot (@dependabot) rebase |
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v4...v6) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/setup-node-6
branch
from
87b7036 to
fc73ad4
Compare
RemiliaForever (RemiliaForever)
deleted the
dependabot/github_actions/actions/setup-node-6
branch
Shane Holloman (shaneholloman)
pushed a commit
to shaneholloman/nexa-sdk
that referenced
this pull request
Jul 7, 2026
…riants When precision=None, ensure_cached now calls query() to resolve the hub's is_default candidate before calling pull(). Previously, passing precision=None to pull() caused the SDK to download every available variant (Q4_0, Q8_0, F16, ...) instead of just the recommended one. The fix mirrors the Go CLI's choosePrecision() logic: query first, then pull with the single winning precision. The query() call is skipped when the caller already supplied a precision, when a local_path is given (manifest already on disk), or when query() itself fails (offline / unsupported hub) — in those cases pull() proceeds unchanged. Closes qualcomm#1098 (cherry picked from commit 4c421dc41e0f34f3f378f86649e5482a6868aaaf)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps actions/setup-node from 4 to 6.
Release notes
Sourced from actions/setup-node's releases.
... (truncated)
Commits
48b55a0Update Node.js versions in versions.yml and bump package to v6.4.0 (#1533)ab72c7eUpgrade@actionsdependencies (#1525)53b8394Bump minimatch from 3.1.2 to 3.1.5 (#1498)54045abScope test lockfiles by package manager and update cache tests (#1495)c882bffReplace uuid with crypto.randomUUID() (#1378)774c1d6feat(node-version-file): support parsingdevEnginesfield (#1283)efcb663fix: remove hardcoded bearer (#1467)d02c89dFix npm audit issues (#1491)6044e13Docs: bump actions/checkout from v5 to v6 (#1468)8e49463Fix README typo (#1226)